Update subscribe-to-graph-api-events.md#128386
Update subscribe-to-graph-api-events.md#128386akhudairymicrosoft wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Created event is not supported by Graph. https://learn.microsoft.com/en-us/graph/api/resources/subscription?view=graph-rest-1.0#properties
|
@akhudairymicrosoft : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 1c7a783: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the Event Grid + Microsoft Graph subscription documentation to remove unsupported Created change type and align example event types with what Microsoft Graph subscriptions can emit.
Changes:
- Removes
Createdfrom the example Microsoft Graph subscriptionchangeType. - Updates the routing example to avoid
Microsoft.Graph.UserCreatedevent type. - Clarifies
changeTypevalid values and notes thatCreatedisn’t supported.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - You're developing an event-driven solution that uses events from Microsoft Entra ID, Outlook, or Teams to react to resource changes. You need the robust event-driven model and publish-subscribe capabilities that Event Grid provides. For an overview of Event Grid, see [Event Grid concepts](concepts.md). | ||
| - You want to use Event Grid to route events to multiple destinations using a single Graph API subscription and you want to avoid managing multiple Graph API subscriptions. | ||
| - You need to route events to different downstream applications, webhooks, or Azure services based on some properties in the event. For example, you might want to route event types such as `Microsoft.Graph.UserCreated` and `Microsoft.Graph.UserDeleted` to a specialized application that processes users' onboarding and off-boarding. You might also want to send `Microsoft.Graph.UserUpdated` events to another application that syncs contacts information, for example. You can achieve that using a single Graph API subscription when using Event Grid as a notification destination. For more information, see [event filtering](event-filtering.md) and [event handlers](event-handlers.md). | ||
| - You need to route events to different downstream applications, webhooks, or Azure services based on some properties in the event. For example, you might want to route event types such as `Microsoft.Graph.UserUpdated` and `Microsoft.Graph.UserDeleted` to a specialized application that processes users' onboarding and off-boarding. You might also want to send `Microsoft.Graph.UserUpdated` events to another application that syncs contacts information, for example. You can achieve that using a single Graph API subscription when using Event Grid as a notification destination. For more information, see [event filtering](event-filtering.md) and [event handlers](event-handlers.md). |
There was a problem hiding this comment.
This example now mentions Microsoft.Graph.UserUpdated twice (routing to both a specialized app and another app), which makes the scenario ambiguous. Consider adjusting the example so each destination gets a distinct event type (e.g., UserDeleted to off-boarding, UserUpdated to contact sync), and rewording “onboarding” since that typically maps to a create lifecycle that’s no longer applicable here.
| - You need to route events to different downstream applications, webhooks, or Azure services based on some properties in the event. For example, you might want to route event types such as `Microsoft.Graph.UserUpdated` and `Microsoft.Graph.UserDeleted` to a specialized application that processes users' onboarding and off-boarding. You might also want to send `Microsoft.Graph.UserUpdated` events to another application that syncs contacts information, for example. You can achieve that using a single Graph API subscription when using Event Grid as a notification destination. For more information, see [event filtering](event-filtering.md) and [event handlers](event-handlers.md). | |
| - You need to route events to different downstream applications, webhooks, or Azure services based on some properties in the event. For example, you might want to route `Microsoft.Graph.UserDeleted` events to a specialized application that processes users' off-boarding. You might also want to send `Microsoft.Graph.UserUpdated` events to another application that syncs contact information. You can achieve that using a single Graph API subscription when using Event Grid as a notification destination. For more information, see [event filtering](event-filtering.md) and [event handlers](event-handlers.md). |
|
|
||
| { | ||
| "changeType": "Updated,Deleted,Created", | ||
| "changeType": "Updated,Deleted", |
There was a problem hiding this comment.
Microsoft Graph subscription changeType values are typically documented as lowercase (updated,deleted), and requests can fail if the service treats these values as case-sensitive. To keep the sample request executable and aligned with Graph docs, update this to the documented casing.
| "changeType": "Updated,Deleted", | |
| "changeType": "updated,deleted", |
| --- | ||
|
|
||
| - `changeType`: the kind of resource changes for which you want to receive events. Valid values: `Updated`, `Deleted`, and `Created`. You can specify one or more of these values separated by commas. | ||
| - `changeType`: the kind of resource changes for which you want to receive events. Valid values: `Updated`, and `Deleted` (`Created` is not supported by Graph, check Graph documentation for more details). You can specify one or more of these values separated by commas. |
There was a problem hiding this comment.
The valid-values sentence is a bit awkward/grammatically inconsistent (extra comma after Updated, and a parenthetical that reads like an aside). Consider tightening this to “Valid values: updated and deleted.” and linking directly to the Microsoft Graph subscription documentation section for changeType, instead of “check Graph documentation for more details.”
| - `changeType`: the kind of resource changes for which you want to receive events. Valid values: `Updated`, and `Deleted` (`Created` is not supported by Graph, check Graph documentation for more details). You can specify one or more of these values separated by commas. | |
| - `changeType`: the kind of resource changes for which you want to receive events. Valid values: `updated` and `deleted`. `created` isn't supported by Microsoft Graph. For more information, see [Microsoft Graph subscription properties](/graph/api/resources/subscription#properties). You can specify one or more of these values separated by commas. |
Created event is not supported by Graph. https://learn.microsoft.com/en-us/graph/api/resources/subscription?view=graph-rest-1.0#properties